Resolved / Related Issues

• Feature: Improving Performance, optimizations, reliability and codebase  #4180

When selecting files or folders, SelectionChanged is raised multiple times even when the actual selection does not change.
For example, when opening a folder by double-clicking, SelectionChanged is fired repeatedly without any real change in SelectedItems.

The root cause is that SelectedItems was always assigned from a new list instance:

SelectedItems = FileList.SelectedItems.Cast<ListedItem>().Where(x => x is not null).ToList();

Since ToList() creates a new list instance on every call, the setter was always triggered and caused unnecessary side effects (such as PropertyChanged-driven updates).

Steps used to test these changes

• Open a file by double-clicking
• Open a folder by double-clicking
• Open a folder using keyboard navigation
• Select multiple items by mouse